This chapter describes Bootp (BTP) messages. For information on message content and how to use the message, refer to the Introduction.
| BTP.001 |
Level: U-TRACE
Short Syntax: BTP.001 rcvd rqst frm ( client_IP_address, nt Network ID)
Long Syntax: BTP.001 received request from ( client_IP_address, net Network ID)
Description: A BOOTP request has been received on a particular interface. The client IP address is included in the message, but may be unknown at this time, in which case it will show up as 0.0.0.0.
| BTP.002 |
Level: UE-ERROR
Short Syntax: BTP.002 bd rqst frm ( client_IP_address, nt Network ID): reason
Long Syntax: BTP.002 bad request from ( client_IP_address, net Network ID): reason
Description: A BOOTP request has been received on a particular interface. The client IP address is included in the message, but may be unknown at this time, in which case it will show up as 0.0.0.0. The request is bad for the stated reason, and is therefore discarded.
| BTP.003 |
Level: U-TRACE
Short Syntax: BTP.003 fwd rqst to server_IP_address
Long Syntax: BTP.003 Forwarding request to server_IP_address
Description: A BOOTP request is being forwarded to a particular server.
| BTP.004 |
Level: U-TRACE
Short Syntax: BTP.004 fwd rply server_IP_address -> client_IP_address
Long Syntax: BTP.004 Forwarding reply from server_IP_address to client_IP_address
Description: A BOOTP reply is being forwarded from a particular server back to the client, using the router as a relay agent.
| BTP.005 |
Level: UE-ERROR
Short Syntax: BTP.005 bad reply server_IP_address -> client_IP_address: reason
Long Syntax: BTP.005 bad reply from server_IP_address to client_IP_address: reason
Description: A BOOTP reply was received. We are unable to relay the reply to the client due to the stated error. The BOOTP reply has been discarded.
| BTP.006 |
Level: ALWAYS
Short Syntax: BTP.006 net Network ID, gw source_IP_address: Client reply packet in error; error
Long Syntax: BTP.006 net Network ID, gw source_IP_address: Client reply packet in error; error
Description: A reply was received from a BOOTP server that was either the incorrect packet type or it was too short. The gatway address is the router that did the final relay from the server to this client. It could be the server address.
| BTP.007 |
Level: ALWAYS
Short Syntax: BTP.007 net Network ID, Valid Resp, Server: serverName( serverIp), Bootfile: bootfile VendOpts config file: cfgFile IpAddr ourIp, gwAddr gwAddr
Long Syntax: BTP.007 net Network ID, Valid Resp, server: serverName/ serverIp, bootfile: bootfile, vendor options config File: cfgFile, ipAddr ourIp, gwAddr gwAddr
Description: A valid BOOTP reply packet was received from a server.
| BTP.008 |
Level: ALWAYS
Short Syntax: BTP.008 net Network ID No cfg file name (srv: serverName/ serverIp)
Long Syntax: BTP.008 net Network ID No config file name in packet (srv: serverName/ serverIp)
Description: A reply was received from a server without a configuration filename in the vendor extension field or in the boot filename field.
| BTP.009 |
Level: ALWAYS
Short Syntax: BTP.009 net Network ID, Failed to snd client req (htype: htype)
Long Syntax: BTP.009 net Network ID, Failed to send client request (htype: htype)
Description: An attempt to send the BOOTP request failed.
| BTP.010 |
Level: ALWAYS
Short Syntax: BTP.010 net Network ID, Sent client request (htype: htype)
Long Syntax: BTP.010 net Network ID, Sent client request (htype: htype)
Description: A BOOTP client request was successfully sent.
| BTP.011 |
Level: ALWAYS
Short Syntax: BTP.011 net Network ID, Could not snd client req because: error
Long Syntax: BTP.011 net Network ID, Could not send client request because: error
Description: An attempt to send the BOOTP request failed because the output device does not support BOOTP, the device is not up, or a buffer could not be allocated.
| BTP.012 |
Level: ALWAYS
Short Syntax: BTP.012 net Network ID No cfile in vendOptions, using bootfile fld instead
Long Syntax: BTP.012 net Network ID No cfile in vendOptions, using bootfile fld instead
Description: The vendor extensions for the configuration filename was not in the response. The router will use the bootfile name field in its place.
| BTP.013 |
Level: ALWAYS
Short Syntax: BTP.013 net Network ID Unsupported vend tag: vendTag, len: vendLen
Long Syntax: BTP.013 net Network ID Reply received with unsupported vendor tag field: vendTag, len vendLen
Description: The server sent a BOOTP reply packet with a vendor field containing an unsupported vendor specific option. This is not critical; it only means that the BOOTP server is not configured correctly for this BOOTP client.
| BTP.014 |
Level: U-TRACE
Short Syntax: BTP.014 cached rqst frm client_hardware_address
Long Syntax: BTP.014 cached request from client_hardware_address
Description: A BOOTP client request was cached.
| BTP.015 |
Level: U-TRACE
Short Syntax: BTP.015 rmvd cached rqst frm client_hardware_address: reason
Long Syntax: BTP.015 removed cached request from client_hardware_address: reason
Description: A BOOTP client request was removed from the cache.
| Panic btpudperr |
Short Syntax: bootp udp port not avail
Description: Another application registered previously with bootp's UDP port.
Action: Contact customer service.